Looking it over, but as an initial complete aside - you can set the Model's returnType to the class name you want returned, and save you the effort of populating the entities yourself. So, in your model:

protected $returnType = 'App\Entities\UserCoursesEntity';

Uhmm. Thanks! Day of testing here. 😄

What about the $this->response->setLink()?

The problem I"m having so far is that the small handful of documents that I've Googled use stylesheets as examples, or resources in an Atom feed. Neither of those are specific to the pager. While I'm not opposed to adding the setLink() on the response, it should be generic enough to work in all of the intended use cases. If that can't be done, then there's no need for a specific call built into the framework.

To be honest, in the decade I've been building apps I've never had a need for this header, so it sounds like maybe something left to app-specific usage. You can always make a custom method in the controller or even use your own Response class that extends the built in one.

Got it. I'm very new to REST. I made this inspired by the GitHub API documentation and thought it would be useful in most cases.

I'll have to think on the formatting later, but something built into the API/ReponseTrait dealing with the paging could be very helpful.

I'm modifying a CI3 api at the moment where I need to implement this somehow. For mobile apps especially, all the little savings in processing add up. I haven't tested natanfelles implementation here but it's a feature I'd use if it were available.

https://gist.github.com/natanfelles/5175e0544ff471fa90f2354327631b8c

If something like that will be implemented, it could be done on the fly:

/**
 * Get pagination links for head - SEO
 *
 * @param \CodeIgniter\Pager\Pager|null $pager
 *
 * @see https://webmasters.googleblog.com/2011/09/pagination-with-relnext-and-relprev.html
 *
 * @return string
 */
public function renderPaginationLinks(\CodeIgniter\Pager\Pager $pager = null):string
{
	if ($pager instanceof \CodeIgniter\Pager\Pager)
	{
		$links = PHP_EOL;

		// Previous
		if ($pager->getPreviousPageURI())
		{
			$links .= '<link rel="prev" href="'. $pager->getPreviousPageURI() . '">' . PHP_EOL;
		}

		// Current
		$links .= '<link rel="canonical" href="'. $pager->getPageURI($pager->getDetails()['currentPage']) . '">' . PHP_EOL;

		// Next
		if ($pager->getNextPageURI())
		{
			$links .= '<link rel="prev" href="'. $pager->getNextPageURI() . '">' . PHP_EOL;
		}

		return $links;
	}

	return PHP_EOL . '<link rel="canonical" href="' . \current_url() . '">' . PHP_EOL;
}

Hi, if this feature is not necessary we can close this PR.

Coming back to this after quite a while. Looking it over again, and thinking it through, I think I'm ok with this feature being in the system. This simply acts as a helper for what you can do anyway ($response->setHeader()) and makes it simpler to use for pagination.

@natanfelles if you want to get this working with the current code base I'm cool with it.